Citrix XenApp/XenDesktop Monitoring
Last updated on 30 September, 2024Overview
Citrix XenApp/XenDesktop monitoring covers three components:
- Desktop Data Collectors (DDC). Also known as Brokers, these DataSources provide information about the state of their services, connections to their datastores, and hypervisors.
- The Farm. Provides information for farm-level entities such as applications, desktop groups, Virtual Delivery Agent registrations, etc. All farm monitoring is done through the DDCs.
- Virtual Delivery Agent (VDA). Enhanced session monitoring for metrics such as RoundTripTime and Throughput are performed if Virtual Delivery Agents have been added to LogicMonitor.
| DataSource | Coverage | Description |
| Citrix_XenApp_Machines | Farm | Monitor machines (VDAs) belonging to the Farm |
| Citrix_XenApp_LogonPerformance | Farm | Monitor logon performance; logon performance is aggregated per delivery group |
| Citrix_XenApp_Troubleshooter | DDC | Find issues that might impede monitoring |
| Citrix_XenApp_ConnectionFailureTrends | Farm | Breakdown of connection failure trends by the reason for failure |
| Citrix_XenApp_MachineFailureTrends | Farm | Breakdown of machine failure trends by reason for failure |
| Citrix_XenApp_DatastoreStatus | DDC | Monitor a DDC’s data connection to the datastore |
| Citrix_XenApp_ApplicationUsage | Farm | Monitor application launch data |
| Citrix_XenApp_MachineCatalogs | Farm | Monitor machine catalog utilization |
| Citrix_XenApp_UserExperience | VDA | User experience metrics such as RoundTripTime, Bandwidth and latency |
| Citrix_XenApp_HypervisorConnections | DDC | Verify that the DDCs have control of the configured hypervisors |
| Citrix_XenApp_DeliveryGroups | DDC | Monitor delivery group utilization and availability |
Setting up Monitoring
- Create or identify a XenApp user account that has read-only administrator privileges that LogicMonitor will use to access XenApp/XenDesktop.
- Within LogicMonitor, define the properties
xenapp.userandxenapp.passon the global, group, or DDC device level, matching the XenApp user account name and password. These properties must be set in order for collection to work, even if the Collector service account has the same access.- (Optional)
Citrix.VAD.SecureHostnamecan be set to the value in the certificate if it is different from the value of system.hostname. - For more information on setting authentication credentials as properties, see Defining Authentication Credentials.
- (Optional)
- To enable PowerShell SDK-based collection methods (the
Citrix_XenApp_DatastoreStatusandCitrix_XenApp_HypervisorConnectionsDataSources rely on PowerShell), make sure that the Collector account has Farm credentials (these can be the same credentials used for thexenapp.userandxenapp.passproperties). - Import the DataSources and PropertySources.
- All of the Citrix DataSources start with
Citrix_XenApp_*. - The
addCategory_CitrixMonitorServiceV2PropertySource must also be imported.
- All of the Citrix DataSources start with
- Because we should only collect FARM information from one of the DDCs, we have to determine which one that will be. This is done by setting “CitrixBrokerActive” as the value for the
system.categoriesproperty on the DDC from which data collection will take place. - (Optional) By default, LogicMonitor uses HTTP to connect to the XenApp modules. You can enable HTTPS connections by setting the resource property
Citrix.VAD.HTTPS = true.